Automatic capturing of multi-mode inputs in applications

ABSTRACT

A method includes: detecting activation, on a device, of a content capturing and presenting (CCP) interface for receiving content that can be inputted via both speech-input and tactile-input; and in response to the activation, automatically enabling both (i) a tactile input mechanism for capturing tactile inputs and (ii) a microphone for capturing audible speech inputs. The method further includes: monitoring for detection of one of (i) a tactile input, which involves use of the tactile input mechanism to input the content and (ii) audible speech, which triggers use of the microphone to input the content; and in response to detecting audible speech: closing the tactile input mechanism; capturing the audible speech via the microphone; and presenting content corresponding to the audible speech within the CCP interface.

BACKGROUND

1. Technical Field

The present disclosure generally relates to interfacing withapplications executing on user devices, and in particular to a methodand device for automated capture of inputs within an interface of anapplication executing on a user device.

2. Description of the Related Art

One very common usage of electronic user devices, such as smart phones,tablets, and computers, is for execution of applications that require auser to provide textual inputs into a user interface. Increasingly,these devices are being provided with microphones and the capability toprovide speech input in addition to and/or in place of textual inputs.This usage is becoming increasing popular with standard messagingapplications, such as provided with short message service (SMS) orinstant messaging applications. Many of the user interfaces for theseapplications now provide a virtual microphone displayed within themessage interface or as a selectable icon included on a virtualkeyboard. However, the default input mechanism for these applicationshave remained the keyboard, which requires tactile manipulation of thedevice. Thus, access to the microphone and, by extension, access tospeech-based interfacing with these applications, first require a manualor tactile input to open the message interface and or reply message,manually activate the keyboard, and then, if speech input is desired,manually activate and/or select the microphone as an input mechanism.Given that the microphone is a preferred means of some users forproviding input to these applications, the experience is fragmented andmostly manual user interface and/or touch driven, although the userultimately wants or prefers to use speech as the means for providing theinput. Similar limitations exist in other computer applications such astraditional word processing software and other applications that receivetext-based input, but which can be manually configured to support userdictation of speech input.

BRIEF DESCRIPTION OF THE DRAWINGS

The description of the illustrative embodiments can be read inconjunction with the accompanying figures. It will be appreciated thatfor simplicity and clarity of illustration, elements illustrated in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements are exaggerated relative to otherelements. Embodiments incorporating teachings of the present disclosureare shown and described with respect to the figures presented herein, inwhich:

FIG. 1 provides a block diagram representation of an example electronicdevice configured with various hardware, firmware and softwarecomponents that enable various features of the disclosure, according toone or more embodiments;

FIG. 2 illustrates a multi-level device view depicting functionalhardware, firmware, and software components within specific levels thatcollectively enable automatic activation of dual input mechanisms withina messaging application environment provided on a user device, accordingto one or more embodiments;

FIG. 3 is a block diagram illustration of an example laptop providing aword processing application interface and which supports the automaticactivation of audible speech input on opening of the application, inaccordance with one or more embodiments;

FIGS. 4-9 provide different temporal views of a messaging interface onan example handheld user device, such as a mobile phone, illustratingthe automatic activation of the dual inputs, including a tactile userinterface and virtual microphone, as well as other associatedfunctionality within the messaging interface, in accordance with severalembodiments;

FIG. 10 is a flow chart illustrating an example method of automaticallyactivating and controlling both tactile input and speech input on adevice and responding to detection of a specific one of the inputs, inaccordance with one or more embodiments;

FIG. 11 is a flow chart illustrating an example method of implementingthe automatic activation of dual input mechanisms within a device andseveral additional features associated therewith within a messagingapplication, in accordance with one or more embodiments; and

FIG. 12 is a flow chart of an example method of automatically creating areply message from audible input and automatically forwarding that replymessage, based on tracking the elapsed time from a last received input,in accordance with one or more embodiments.

DETAILED DESCRIPTION

The illustrative embodiments of the present disclosure provide a methodand device that enables automatic activation of both a tactile inputmechanism and a speech input mechanism in response to opening of anapplication interface that allows for receipt of both types of inputs.

According to one aspect, the method includes: detecting activation, on adevice, of a content capturing and presenting (CCP) interface forreceiving content that can be inputted via both speech-input andtactile-input; and in response to the activation, automatically enablingboth (i) a tactile input mechanism for capturing tactile inputs and (ii)a microphone for capturing audible speech inputs. The method furtherincludes: monitoring for detection of one of (i) a tactile input, whichinvolves use of the tactile input mechanism to input the content and(ii) audible speech, which triggers use of the microphone to input thecontent; and in response to detecting audible speech: closing thetactile input mechanism; capturing the audible speech via themicrophone; and presenting content corresponding to the audible speechwithin the CCP interface.

In the following detailed description of exemplary embodiments of thedisclosure, specific exemplary embodiments in which the various aspectsof the disclosure may be practiced are described in sufficient detail toenable those skilled in the art to practice the invention. For example,specific details such as specific method orders, structures, elements,and connections have been presented herein. However, it is to beunderstood that the specific details presented need not be utilized topractice embodiments of the present disclosure. It is also to beunderstood that other embodiments may be utilized and that logical,architectural, programmatic, mechanical, electrical and other changesmay be made without departing from the spirit or scope of the presentdisclosure. The following detailed description is, therefore, not to betaken in a limiting sense, and the scope of the present disclosure isdefined by the appended claims and equivalents thereof.

It is understood that the use of specific component, device and/orparameter names, such as those of the executing utility, logic, and/orfirmware described herein, are for example only and not meant to implyany limitations on the described embodiments. The embodiments may thusbe described with different nomenclature and/or terminology utilized todescribe the components, devices, parameters, methods and/or functionsherein, without limitation. References to any specific protocol orproprietary name in describing one or more elements, features orconcepts of the embodiments are provided solely as examples of oneimplementation, and such references do not limit the extension of theclaimed embodiments to embodiments in which different element, feature,protocol, or concept names are utilized. Thus, each term utilized hereinis to be given its broadest interpretation given the context in whichthat terms is utilized.

References within the specification to “one embodiment,” “anembodiment,” “embodiments”, or “one or more embodiments” are intended toindicate that a particular feature, structure, or characteristicdescribed in connection with the embodiment is included in at least oneembodiment of the present disclosure. The appearance of such phrases invarious places within the specification are not necessarily allreferring to the same embodiment, nor are separate or alternativeembodiments mutually exclusive of other embodiments. Further, variousfeatures are described which may be exhibited by some embodiments andnot by others. Similarly, various requirements are described which maybe requirements for some embodiments but not other embodiments.

As further described below, implementation of the functional features ofthe disclosure described herein is provided within processing devicesand/or structures and can involve use of a combination of hardware,firmware, as well as several software-level constructs (e.g., programcode and/or program instructions and/or pseudo-code) that execute toprovide a specific utility for the device or a specific functionallogic. The presented figures illustrate both hardware components andfirmware and software and/or logic components.

Those of ordinary skill in the art will appreciate that the hardwarecomponents and basic configurations depicted in the figures may vary.The illustrative components are not intended to be exhaustive, butrather are representative to highlight essential components that areutilized to implement aspects of the described embodiments. For example,other devices and/or components may be used in addition to or in placeof the hardware and/or firmware depicted. The depicted example is notmeant to imply architectural or other limitations with respect to thepresently described embodiments and/or the general disclosure.

The description of the illustrative embodiments can be read inconjunction with the accompanying figures. It will be appreciated thatfor simplicity and clarity of illustration, elements illustrated in thefigures have not necessarily been drawn to scale. For example, thedimensions of some of the elements are exaggerated relative to otherelements. Embodiments incorporating teachings of the present disclosureare shown and described with respect to the figures presented herein.Also, within the descriptions of the different views of the figures,similar elements are provided similar names and reference numerals asthose of the previous figure(s). The specific numerals assigned to theelements are provided solely to aid in the description and are not meantto imply any limitations (structural or functional or otherwise) on thedescribed embodiment.

Turning now to FIG. 1, there is depicted a block diagram representationof an example device 100 shown communicatively connected within anexample communication environment 105 via one or more of a plurality ofcommunication mechanisms 170. Device 100 includes hardware, firmware,and software components, several of which are utilized to enableimplementation of various features of the disclosure. According to oneimportant aspect, device 100 includes voice/speech input and/or audioinput components that can be automatically activated to enablevoice/speech initiation of the input mechanisms associated with anapplication. The device 100 can be one of a host of different types ofdevices, including but not limited to, a mobile cellular phone orsmart-phone, a laptop, a net-book, an ultra-book, and/or a tabletcomputing device, or even a general desktop or server computing device.These various devices all provide and/or include the necessary hardwareand software to enable tactile input and speech input to an executingapplication. Additionally, in embodiments that support message exchangevia a wired or wireless network, device 100 includes the hardware,firmware, and/or software required to support the various wireless orwired communication functions as part of a multi-participantcommunication environment.

Referring now to the specific illustrated components that make up device100, device 100 can include a processor integrated circuit (IC) 110,which is physically connected, via a plurality of bus interconnects(illustrated by the unidirectional and bi-directional arrows), to aplurality of functional components of device 100. Processor IC 110 caninclude one or more programmable microprocessors, such as a dataprocessor 112 and a digital signal processor (DSP) 110, which may bothbe integrated into a single processing device, in some embodiments.Processor IC 110 can also include one or more controllers, such as userinterface (UI) controller 116 and audio controller 118. Thesecontrollers can be functional modules within data processor 112, in oneembodiment. The processor IC 110 controls the communication, userinterface features, and other functions and/or operations of device 100.These functions and/or operations thus include, but are not limited to,application data processing and signal processing. The presentinnovation can be implemented using hardware component equivalents suchas special purpose hardware, dedicated processors, general purposecomputers, microprocessor based computers, micro-controllers, opticalcomputers, analog computers, dedicated processors and/or dedicated hardwired logic. Additionally, as described herein, certain user interfacingaspects can be completed by UI controller 116, which for purposes of thedisclosure is represented as a physical controller communicativelyconnected to the user interface components, such as the touch screen ofthe device. In alternate embodiments, the functionality of UI controller116 can be provided as a module of code that is executed by theprocessor 112 to generate specific control aspects of the userinterfacing functions of the device. Additionally, when UI controller116 is a separate physical device, UI controller 116 can be located inanother location within device, and not necessarily on processor IC 110,as shown.

Device 100 includes a plurality of input/output (I/O) devices, includingat least one audio input device, microphone 120, at least one audiooutput device, speaker 122, display 124, camera 126, subscriber identitymodule (SIM) and/or storage card 128, and at least one tactile inputmechanism 130. When device 100 is a mobile phone that incorporates a SIM128, SIM 128 provides unique identification of the subscriber that ownsor utilizes the device 100, as well as specific additional informationassociated with the particular subscriber and/or service. According toone aspect of the disclosure, the tactile input mechanism 130 providestext content in response to user manipulation of an input affordancethat is associated with one of the device and an executing application.The tactile input mechanism 130 can include a touch screen 132, whichcan be utilized to display a one or more of a virtual keyboard/keypad, atouchpad, or a swype screen. Tactile input mechanism 130 can alsoinclude a physical touch pad 134, a physical keyboard or keypad 136,and/or a pointing device 138. While shown as a physical component ofdevice 100, pointing device 138, such as a mouse or stylus, is typicallyexternally connected to device 100 via a wired or wireless communicationinterface. Similarly, when device is a not a singular device, such as amobile phone, tablet, or laptop, several others of the I/O componentscan be located external to physical device casing (not shown) housingthe processor IC 110. Device 100 also includes system clock 140, whichserves as a chronometer or basis for all timers, as utilized in thedisclosed embodiments. Also, power supply 145 provides required powerfor operating the individual components within device 100 and, byextension, for powering device 100 as a whole.

Connected to processor IC 110 is storage 150 and memory 160, which caninclude volatile memory and/or non-volatile memory. Storage 150 is apermanent data storage device, which can be any type of availablestorage device capable of storing one or more application software(program code) and data. It is further appreciated that in one or morealternate embodiments, storage 150 can actually be remote storage andnot an integral part of the device itself. Storage 150 can includerandom access memory and other types of non-volatile memory. Storage 150maintains the executable modules for system firmware 152, as well as themodules of one or more applications that can be executed on device 100.System firmware 152 can include general device firmware 153 and otherfirmware that are associated with device 100 and which provides/performsor supports several of the functional features of the presentdisclosure, according to the described embodiments. For example, systemfirmware 152 is illustrated having included therein speech-to-textengine 154, automatic dual input activation utility 155, speech/audioinput detection module 156, and I/O devices control firmware modules158. It should be appreciated that the specific names of the modules ofcode that implement the specific functions described are not necessarilyactual names applied to the modules of executable code, and the namesprovided are intended merely to provide a functional description of theoperations performed by the specific module of executable firmware code.

Referring now to memory 160, during device operation, the executablecode of firmware modules and/or from executable applications can beloaded into memory for execution by data processor 112. Specifically,memory 160 is illustrated as containing executable code of firmware 152and executable code of example application 162, which includes anapplication (user) interface 163 that supports or incorporates a contentcapturing and presenting (CCP) interface 164. In at least theillustrated embodiment, application 162 can also include a tactile inputmodule 165 and an audible speech input module 166 for displaying virtualinput mechanisms that can be used to receive corresponding tactileand/or audible speech inputs.

In addition to the above executable code/program modules of application162, memory 150 can include additional modules associated with eitherapplication 162 or system firmware 152. In the illustrative embodiment,these modules, including flashing microphone icon module 167 and virtualtactile input module 168, are presented within system firmware 152.However, it is appreciated that the functionality associated with one orboth modules can be included within the program code of application 162,in alternate embodiments. Flashing microphone icon module 167 can becontrolled by UI controller 116, which is in communication with a speechinput (or voice) detection and receiving subsystem that consists ofmicrophone 120 and audio controller 118. Virtual tactile input module132 communicates with and/or is controlled by UI controller 116. Theassociated functionality and/or usage of each of the software moduleswill be described in greater detail within the descriptions whichfollow. In particular, the functionality associated with and/or providedby the UI controller and the user interface modules is described ingreater details with the description of the remaining figures, beginningwith FIG. 2.

Continuing with FIG. 1, as a part of a communication network 105, device100 includes one or more communication components to support the wiredand/or wireless communication aspects of the disclosure. As shown,communication mechanisms 170 includes wireless wide area network (WWAN)transceiver 172 with connected antenna 173 and which communicates with aradio access network (RAN) 182 of a cellular network 180. RAN 182 isgenerally represented as including a base station, depicted as anevolved base node (“eNodeB”) 183 controlled by a radio networkcontroller (RNC) 184 that transceives (i.e., transmits and receivescommunication signals) over a base station antenna 185. To reducecluttering of the figure, only one connected antenna 173 is depicted.However, device 100 may contain more than one antenna, each antennahaving one or more selected bandwidths of operation to support differentmodes of communication or for simultaneous communication in differentcommunication technologies.

Alternatively or in addition to WWAN transceiver 172, device 100 caninclude a wireless local access network (WLAN) module 174 to communicatewith wireless devices and network, accessible via a wireless accesspoint 190. Alternatively or in addition, device 100 can include awireless personal access network (WPAN) transceiver 178 to communicatewith WPAN devices, depicted as a Bluetooth® headset 193. WPAN caninclude technologies such as IrDA, Wireless USB, Bluetooth®, Z-Wave,ZigBee, Body Area Network, and ANT+. Alternatively or in addition,device 100 can include a near field communication (NFC) transceivermodule 179, such as can be utilized for exchanging files with anotheruser device or a payment kiosk, for example.

As a device supporting wireless communication, device 100 can be one of,and be referred to as, a system, device, subscriber unit, subscriberstation, mobile station (MS), mobile, mobile device, remote station,remote terminal, user terminal, terminal, communication device, useragent, cellular telephone, a satellite phone, a cordless telephone, aSession Initiation Protocol (SIP) phone, a wireless local loop (WLL)station, a personal digital assistant (PDA), a handheld device havingwireless connection capability, a computing device, such as a laptop,tablet, smart phone, personal digital assistant, or other processingdevices connected to a wireless modem.

As further illustrated, device 100 can also include components for wiredcommunication, such as modem 175 for communicating over a plain oldtelephone system (POTS) 188 and Ethernet module 177 for connecting to alocal access network (LAN) 192. Collectively, these wireless and wiredcomponents provide communication mechanisms 194 by which device 100 cancommunicate with the network 105 and particularly with other userdevices within the networks. As illustrated at the top of FIG. 1,communication network 105 can include a second user device 187 belongingto a second user 186. In the description which follows, second user 186and/or his device 187, are referred to as another messaging participant,with the assumption being that the application being executed on thedevice 100 can be a messaging application (e.g., SMS or IM) that has amessaging interface for displaying and receiving content that canoriginate at the device 187 of second user 186.

Turning now to FIG. 2, there is illustrated a multi-level configurationseparating out components within device 100. The multi-levelconfiguration includes hardware level 210, firmware level 220,application level 240, and user interface level 250, extending from thebottom of the figure to the top of the figure. Many of the physicalhardware, firmware and software components overlap with those shown inFIG. 1 and have been previously introduced. Reference is made to thesecomponents only as need to complete the description of FIG. 2. Similarreference numerals are presented for those previously-introducedcomponents. Beginning at the hardware level 210, the various componentsincluded therein have been previously introduced in the description ofFIG. 1. Moving up to firmware level 220, there are illustrated severaladditional components in addition to the already-introduced componentsfrom FIG. 1. Thus, firmware level 220 includes operating system (OS) 222and basic input output system (BIOS) 224. These components are common inthe industry, particularly within general computer systems and smartdevices that support execution of multiple applications. In addition tothese primary firmware components and/or as a complement to BIOS 224,firmware level 220 includes I/O device control firmware/modules 226,which are often referred to in the industry as device drivers. In theillustrative embodiment, I/O device control firmware/modules 226includes specific UI controller firmware 228 that supports certain ofthe user interface functions described herein. It is appreciated thatthe firmware (228) for UI controller 118 can be embedded or storedwithin UI controller itself, and can exist independent of the devicefirmware, in alternate embodiments. Firmware level 220 also includesdual input support firmware 230, comprising multiple executable modules,which collectively support and/or implement several of the various novelfeatures of the disclosure. In addition to the previously introducedmodules, dual input support firmware 230 also includes tactile inputdetection monitor 231, timer 232, first response time threshold 233, andsecond response time threshold 234.

First response time threshold 233 and second response time threshold 234are pre-established time values that can, in one embodiment, be setand/or modified by a user of device, either at a device level and/or ata specific application level. It is appreciated that not everyapplication that utilizes the functionality described herein wouldoperate on a same wait time for detection of speech or other inputs. Forexample, a messaging application would perhaps require a shorter waittime for receipt of audible input than the wait time assigned to a wordprocessing application. Thus, application-based setting of the specificwait times to utilize for the particular application can be provided, asone aspect of the disclosure.

In certain embodiments, dual input support firmware 230 can also includeautomatic message read out (AMRO) utility 235. As described in greaterdetail below, AMRO utility 235 enables automatic reading out of certaintypes of content displayed within the messaging interface 252 followingactivation or opening of the messaging interface 252 and/or opening ofone or more included message elements 254. In one embodiment, theautomated read-out occurs based on a set of one or more pre-establishedconditions. In the following description of the one or more exampleembodiments, AMRO utility 235 is presented as a module within thefirmware 152 of device 100 and thus separate from and not includedwithin application 162. However, embodiments are contemplated in whichAMRO utility 235 is provided as an executable component withinapplication code. Firmware level 220 also includes a text-to-speechengine 236, which can be included within dual input support firmware230, in one embodiment.

According to the general aspects presented by the present disclosure,the combination of FIGS. 1 and 2 provides a device 100 that includes aplurality of input devices, including a speaker 122, a microphone 120capable of capturing audible speech inputs, and at least one tactileinput mechanism 130. The device includes: a display device 124 capableof displaying a plurality of user interfaces and control affordances;and a memory 160 comprising firmware 152 and at least one application162 that generates a content capturing and presenting (CCP) interface164 for receiving content that can be inputted via both speech-input andtactile-input. The device also includes a processor 112 that iscommunicatively coupled to the speaker 122, the microphone 120, thedisplay device 124, the tactile input mechanism 130, and the memory 160,and which executes program code of the firmware 152 and the application162 to activate the CCP interface 164. The device 100 also includes auser interface controller 118 communicatively connected with theplurality of input devices and the processor 112 and that detectsactivation of the CCP interface 164. Accordingly, during operation ofthe device to execute the application, the user interface controller118, in response to detecting the activation of the CCP interface 164,triggers activation of both (i) the tactile input mechanism 130 forcapturing tactile inputs and (ii) the microphone 120 for capturingaudible speech inputs. The user interface controller 118 monitors fordetection of one of (i) a tactile input, detected at the tactile inputmechanism 130, which would require/involve use of the tactile inputmechanism to input the content, and (ii) audible speech, captured viathe microphone 120, which triggers use of the microphone 120 to inputthe content. Following, in response to detecting audible speech, theuser interface controller 118: closes or de-activates the tactile inputmechanism 130; captures the audible speech via the microphone 120; andpresents content corresponding to the audible speech within the CCPinterface 165.

In a general context, the above aspects of the disclosure can be appliedto any number of applications that allow for user input of text-basedcontent, where the content can also be inputted via speech input. Wherethe resulting content is intended to be alphanumeric text, such as witha word processing application, a speech-to-text engine is utilized totranscribe the received audible speech into text. The resulting text isthen presented within the CCP interface 164 as the content. Inembodiments where speech audio is an acceptable form of content, theaudio file can be provided as the content. These latter embodimentsapply to instances where the application is a messaging application thathas received a speech-based message element that is or can be outputtedon the device speaker 122.

According to one or more embodiment, and as also illustrated by FIG. 6,contemporaneously with automatically enabling the microphone 120, theuser interface controller 118 provides user-detectable indication/s thatthe microphone 120 is in active listening mode, by performing at leastone of (i) displaying an animated icon of the microphone 120, outputtingan audible tone, (iii) performing a speech readout, and (iv) vibratingthe device. Further aspects of this implementation are described withreference to FIGS. 4-8.

FIG. 3 illustrates one embodiment of the general features of thedisclosure applied to a word processing application on a computerdevice. Computer device 300 includes substantially all of the componentsillustrated in FIG. 1 and the hardware and firmware levels of FIG. 2.Computer device 300 is shown as a laptop having a base 310 connected toa display 320. Base 310 includes keyboard 132 and touch pad 134. Amicrophone and speaker are embedded within base 310 and/or display 320,hidden behind the exterior casing of computer 300. Display 320 providesa user interface, which includes a CCP interface 164 of a wordprocessing application. Also presented within the user interface is ablinking microphone icon 325, indicating that the microphone is inactive listening mode. The microphone can be automatically triggered forpresentation on the display contemporaneously with the activation of theapplication and/or the opening of the CCP interface 164 on display 320.Audible notification or tactile notification (via vibration of thedevice, for example) of the activation of the microphone can also beprovided in alternate embodiments. Following opening of the CCPinterface 164, the microphone is automatically activated, and the usercan immediately begin dictating speech audio, which is captured,converted to text, which text is then presented within the CCP interface164.

Returning now to FIG. 2, in one specific implementation of thedisclosure, embodiments are presented in which the application is amessaging application, such as an SMS or IM application, that bothreceives messages from a message sender and enables a user of device 100to reply to the messages and/or to generate new messages using either orboth tactile input and speech input. As provided within FIG. 2, device100 further includes application level 240, which is illustrated havingmessaging application 242, as a specific embodiment of application 162.Messaging application 242 includes a messaging interface, a tactileinput module 246, such as a virtual keyboard that includes a microphoneicon thereon. Messaging application 222 can, in one or more embodiments,include the mechanism for converting audible speech input 228 encodedwithin the application itself. Application level also includes virtualtactile input module 246 and can optionally include automatic messageread out utility 248.

Device 100 also includes user interface level 250, which provides a listof visible components that are presented on the display 124 of thedevice 100 based on actual execution of code within the applicationlevel 240. User interface level 250 is described in conjunction withFIGS. 4-9, which illustrate an example user device 400, such as but notlimited to a smart phone, having a touch screen user interface 410within which is displayed the various components that are introduced inuser interface level 250 (FIG. 2). As illustratively provided withinFIGS. 4, 5 and 6, within user interface level 250 are messaginginterface 252, which includes message elements 253 and input receivingarea, CCP interface 254. User interface level 250 also includes flashingmicrophone icon 260 and virtual keypad 265 that are both selectivelydisplayed based on one or more events, as described herein.

Referring to FIG. 4, there is illustrated example user device 400 withmessaging interface 252 opened and displayed on device 400. Device 400is configured with the various components from FIGS. 1 and 2, of whichspeaker 122 and microphone 120 are illustrated. Device can also includeother external control affordances, such as volume control 415, and alsoincludes virtual affordances, such as settings icon 405, return icon425, and home icon 430. In one or more embodiments, a device settingincludes a default reply setting that supports a text-based reply to thereceived message and is configurable to a second reply setting thatenables user selection of the microphone for speech-based reply whenresponding to the received message, based on detection of userinitiation of audible speech following audible outputting of thereceived message. Also, the device setting can include a setting thatsupports reading out of received messages. Access is provided to thedevice settings interface (not shown) via selection of the settings icon430, in one embodiment or from a menu option, in an alternateembodiment. From that settings interface, a specific firmwareconfiguration can be selected by the user that modifies the defaultconfiguration from a text-only input to a dual input configuration, forlegacy devices, or vice versa, for newer devices that are pre-configuredto provide activation of the dual input methods on instantiation of theapplication or opening of the associated messaging interface.

The opening of messaging interface 252 can be triggered by userselection of an icon or executable file corresponding to messagingapplication 222. In response to that selection, processor 116 executesthe relevant application code along with code of supporting devicefirmware to enable messaging application 222 and to display messaginginterface 252 on the device 400. Messaging interface 252 opens with apresentation of the most recently active message elements 254 on displayscreen 410. Each message element 254 includes an identifier, which mayinclude the name and/or phone number and/or email address and/ornickname of the user that created the particular message element. Forsimplicity, the identifiers are presented simply as the sequentialnumber of the particular message element within the messaging interface252. FIG. 4 also illustrates a user 275 and a finger 420 associated withthat user 275 that is utilized as a tactile message selector. It isappreciated that other types of tactile message selectors are possibleto provide tactile input to the messaging interface 252 of device 400.It is further appreciated that in some embodiments, the opening of themessaging interface 252 can also trigger the activation of themicrophone 120 to allow for voice-activated control of the selection ofa specific message to open. In the provided embodiment, user 420manually selects message element 6, which selection causes the openingof a hierarchical/historical view of message element 6, as shown in FIG.5.

FIG. 5 illustrates one aspect of the embodiment in which CCP interface164 is a part of messaging interface 252. Contemporaneously with theopening of message element 6, UI controller 118 and/or processor 112activates tactile input mechanism and UI controller and/or processor 112and/or audio controller 116 activates microphone 120. The messagingelement is presented with a CCP interface 164 for displaying anyreceived input and a send icon 550 that can be manually selected totransmit the received input within CCP interface 164 as a reply messagein the message sequence. In one embodiment, when a new message is beingcreated (i.e., the input is not being entered for an already existingmessaging element), the messaging interface 252 will include and displayan addressee/recipient section for inputting the identifier of therecipient of the received input message. In the illustrative embodiment,during execution of messaging application, the user interface controller118: detects activation of a message element 254 within a messagingapplication that supports a messaging respondent (user 320) replying toa received message 420 via both speech-input and tactile-input.

Messaging element 6 410 includes therein three received messages,messages 1, 3 and 4, and one transmitted message, message 2. The twomost recent received messages are indicated as having been received“today” and, for the purpose of the illustrative embodiment, anassumption is made that both message 3 and message 4 have not yet beenindividually accessed and/or read by the device or device user.

According to one embodiment, contemporaneously with automaticallyenabling the microphone, the user interface controller 118 can provideuser-detectable indication/s that the microphone is in active listeningmode, by at least one of (i) displaying an animated icon 540 of themicrophone 120 (as illustrated by FIG. 5), (ii) outputting an audibletone 560 (FIG. 5), (iii) performing a speech readout 570 (FIG. 5), and(iv) vibrating the device (580, FIG. 5).

As presented above in the description of FIG. 1, the tactile inputmechanism 130 can include at least one of a physical keyboard, a virtualkeyboard, and a virtual swipe box. Also, the tactile input mechanism 130provides text content in response to user manipulation of an inputaffordance that is associated with one of the device and theapplication.

According to one embodiment, when the tactile input mechanism is avirtual device, the user interface controller 118 simultaneously opensand displays both an icon 540 representing the microphone 120 and avirtual tactile input device (TID) 720. The processor 112 sets a timerto track an elapsed time after the simultaneous opening of the tactileinput mechanism (720) and the microphone 120. Following, in response tothe expiration of the timer without receiving any input, the userinterface controller 118 closes both the tactile input mechanism (720)and the microphone 120. Alternatively, in response to detecting tactilemanipulation of the virtual input device 720 prior to expiration of thetime, the user interface controller 118 removes the microphone icon 540from the display and closes the microphone input (FIG. 9). Further, inresponse to detecting audible speech input prior to expiration of thetimer, user interface controller removes the virtual input device 720from the display.

According to one aspect of the disclosure, the UI controller 118identifies whether a last message (received message 4) within themessage element 254 is a received message. Within the context of thedescribed embodiments, a received message is a message that was createdby another messaging participant (e.g., remote user 186), different fromthe messaging respondent (320), and received within or associated withthe messaging element 254 that corresponds to the messaging respondent.

According to one aspect, in identifying whether a last message withinthe message element is a received message, the processor 112 identifiesa hierarchy of messages within the message element, which hierarchylists an order and time sequence of entry of each message associatedwith the message element, including any messages generated at arespondent side of the message exchange. And, the processor 112identifies as the received message 520 all messages in the hierarchythat were received subsequent to a most recent message generated by themessaging respondent within the message element.

Additionally, in one or more embodiments related to the messaginginterface, in response to the last message within the message elementbeing a received message 520, the user interface controller: identifieswhether the received message has been previously accessed; and inresponse to the received message not having been previously accessed: ifthe received message is in text form, forwards content of the receivedmessage to a text-to-speech engine to covert the text content to audiblespeech; audibly outputs the content of the received message (610, FIG.6); and performs the automatic enabling of the tactile input mechanismand the microphone. Thereby, the received message 520 is audiblyoutputted (610, FIG. 6) contemporaneously with the automaticallyenabling. As one extension of this embodiment, the user interfacecontroller 118 further monitors for detection of an input from among atactile input and an audible speech input during the audible outputtingof the received message. The UI controller 118 pauses the audiblyoutputting of the received message in response to detecting the input.

Further, as illustrated by FIG. 6, in response to multiple receivedmessages not having been previously accessed, processor 112 and/or audiocontroller initiates audible outputting 610 of the multiple receivedmessages 520 in sequential order from a first received to a lastreceived message. Thus, the audible outputting 610 of the content of thereceived message comprises reading out all messages identified as thereceived message 520 in time order of receipt of the messages. Theaudible outputting of the received message/s is illustrated using soundbubble 610 within which the content of the received messages 520 aredisplayed (indicating the messages being audibly read out).

Referring to FIGS. 8 and 9, there are illustrated another view of device400 with audio input received and displayed as corresponding text withinthe CCP interface 164. In this example, the audio content is transcribedto text 810, which is mirrored or presented within the CCP interface 164prior to being transmitted from device 400 to the addressee of themessage. The disclosure allows for pauses during input of messages toallow the speaker to formulate an entire message before the messagecontent is forwarded. Thus, in response to detecting audible speech asthe input method, the user interface controller 118 monitors for a pausein detected audible speech input, and the processor 112 tracks anelapsed time since a last detected audible speech and compares theelapsed time to an end-of-speech input threshold value. In response todetecting additional audible speech input before the elapsed timeexceeds the threshold value, the processor adds content corresponding tothe detected additional audible speech input to previously capturedcontent. Following, the user interface controller 118 and/or theprocessor 112 automatically forwards content corresponding to thecaptured audible speech as a reply message to the received message.Accordingly, the audible speech is audibly captured and the content(810) corresponding to the audible speech is automatically forwarded asthe reply message 910 (FIG. 9), without requiring tactile manipulationof the device. As shown by FIG. 9, the content of the reply message 910is moved from CCP interface 164 to existing message interface 920,displacing the previous last message 520 in the message element tobecome the last current message.

Also, in one embodiment, when the CCP interface 164 is a messaginginterface that captures content for transmission as a message, inresponse to the elapsed time exceeding the threshold value: theprocessor sets a second timer and visually, audible (e.g., sendingmessage signal 820) or otherwise indicates that the content of thereceived audible speech is about to be transmitted to another messagingparticipant. The user interface controller monitors for detection of oneof an audio input and a tactile input prior to expiration of the secondtimer, and in response to not detecting any further input prior toexpiration of the second timer, the processor automatically forwards thecontent (810) of the detected speech presented within the reply message810 to the other messaging participant. However, in response todetecting a tactile input: the user interface controller 116automatically opens the tactile input mechanism and CCP interface (thetext input area of the message) having the content of the detectedaudible speech displayed therein for editing and appending thereto. Theprocessor 112 then forwards a final content of the reply message 810only when a send message option 550 is selected within the messaginginterface.

FIGS. 10-12 are flow charts which illustrate the methods by whichvarious aspects of the disclosure can be implemented, utilizingfunctional components in one or more of the devices presented in FIGS.1-9. Specifically, FIG. 10 illustrates an example method ofautomatically activating and controlling both tactile input and speechinput on a device and responding to detection of a specific one of theinputs, in accordance with one or more embodiments. FIG. 11 illustratesan example method of implementing the automatic activation of dual inputmechanisms within a device and several additional features associatedtherewith within a messaging application, in accordance with one or moreembodiments. And FIG. 12 illustrates an example method of determiningwhen to automatically create a reply message from audible input and whento forward that reply message, based on tracking the elapsed time from alast received input, in accordance with one or more embodiments.

The description of method 1000 is provided with general reference to thespecific components illustrated within the preceding FIGS. 1 and 3. Thedescriptions of methods 1100 and 1200 are provided with generalreference to the specific components illustrated within the precedingFIGS. 1, 2, and 4-9. Generally, methods 1000, 1100 and 1200 aredescribed as being implemented via user interface controller 118 and/orexecution by processor 112 of code provided by application and/orfirmware within device 100, 300, or 400. It is however appreciated thatcertain aspects of the described methods may be implemented via otherprocessing devices and/or device components and/or execution of othercode.

Referring now to FIG. 10, there is presented a method by which dualinput activation is provided for general application processing, inaccordance with one embodiment. Method 1000 begins at start block andproceeds to block 1002 at which method 1000 includes detectingactivation, on a device, of a content capturing and presenting (CCP)interface for receiving content that can be inputted via bothspeech-input and tactile-input. Method 1000 includes, in response to theactivation, automatically enabling both (i) a tactile input mechanismfor capturing tactile inputs and (ii) a microphone for capturing audiblespeech inputs (block 1004). At decision block 1006, method includesidentifying whether the tactile input mechanism is a virtual device.When the tactile input mechanism is a virtual device, method 100 thenincludes simultaneously opening and displaying both an icon representingthe microphone and a virtual tactile input device (TID) (block 1008).FIG. 7 illustrates this opening of both tactile and audible virtualinput mechanisms on the display of the device. Otherwise, method 1000provides opening and displaying the virtual microphone (block 1010).FIG. 5, presented as an illustration of this concept, shows that just avirtual microphone is activated on the device, where there is no virtualtactile input device. Method 1000 then includes providinguser-detectable indication that the microphone is in active listeningmode via at least one method of notification (block 1012). Asillustrated within FIG. 5, the user detectable indication (notification)can include at least one of (i) displaying an animated icon of themicrophone, outputting an audible tone, (iii) performing a speechreadout, and (iv) vibrating the device.

With the microphone automatically activated, method 1000 includes theprocessor setting a timer to track an elapsed time after thesimultaneous activation and/or opening of the tactile input mechanismand the microphone (block 1014). Method further includes monitoring fordetection of one of (i) a tactile input, which involves use of thetactile input mechanism to input the content and (ii) audible speech,which triggers use of the microphone to input the content (block 1016).The user interface controller then determines, at block 1018, whetheruse of a tactile input is detected, and in response to detecting tactilemanipulation of the tactile input device prior to expiration of thetimer, method 1000 includes removing the microphone icon from thedisplay, turning off the audible input notification, and closing orde-activating the microphone input (block 1020).

Further, in response to detecting audible speech input prior toexpiration of the timer, as determined at decision block 1022, method100 includes deactivation and/or closing the tactile input mechanism andremoving (where present) the virtual input device from the display(block 1024). Method 1000 also includes capturing the audible speech viathe microphone ((block 1026) and presenting content corresponding to theaudible speech within the CCP interface (block 1028). Returning todecision block 1022, when no speech input is detected, the timer ischecked (block 1030) to determine whether the elapsed time since theopening of the dual input mechanisms exceeds a preset threshold. Thetimer continues to track the elapsed time, and a periodic check is madeof the elapse time against the time threshold (block 1030). In responseto the time expiring without detecting any tactile or audible speechinput, method 1000 includes closing or de-activating both the tactileinput mechanism and the microphone (block 1032). Subsequently, method1000 includes enabling normal tactile input, which requires tactile userselection of audible input, if the user desires to use audible input(block 1034). Method 1000 then terminates at end block.

Referring now to FIG. 11, there is provided a method by which dual inputactivation is triggered for a messaging application, in accordance withone embodiment. Method 1100 begins at start block and proceeds to block1102 at which method 1100 includes detecting opening of a messageelement within a messaging application. The messaging applicationsupports a messaging respondent replying to a received message via oneor both speech-input and tactile-input. In response to opening of themessaging element, method 1100 includes automatically enabling both atactile input mechanism and a microphone 1104 (block 1104) and providingan indication, via at least one notification mechanism, that themicrophone is in active listening mode (block 1106). Following openingof the message element, method 1100 includes identifying a hierarchy ofmessages within the message element (block 1108). As provided herein,the hierarchy presents an order list in time sequence of entry of eachmessage associated with the message element, including any messagesgenerated at a respondent side of the message exchange. Method 1100 thenincludes identifying whether a last message within the message elementhierarchy is a received message (block 1110). As provided herein, areceived message is a message that was created by another messagingparticipant, typically different from the messaging respondent, andreceived within the messaging element tagged with the identifier of thatother messaging participant. When the last message is a receivedmessage, method further includes determining at decision block 1112whether there are multiple received messages in sequence. In response tothere being multiple received messages in sequence, method 1100 includesidentifying as the received message all messages in the hierarchy thatwere received subsequent to a most recent message generated by themessaging respondent within the message element (block 1114).

Notably, if the received message is in text form, method 1100 caninclude forwarding content of the received message to a text-to-speechengine to covert the text content to audible speech. Then, the method1100 includes audibly outputting the content of the received message(block 1116). In one embodiment, method optionally also includesidentifying whether the received message has been previously accessed,and performing the audibly outputting only in response to the receivedmessage not having been previously accessed. Also, in response tomultiple received messages not having been previously accessed, method1100 can include initiating audible outputting of the multiple receivedmessages in sequential order from a first received message to a lastreceived message. Thus, the audible outputting of the content of thereceived message comprises reading out all messages identified as thereceived message in time order of receipt of the messages. Also, themethod can include audibly outputting the received messagecontemporaneously with the automatically activating or enabling of thetactile input mechanism and the microphone or outputting the receivedmessage prior to the activation of the dual input mechanisms.

At block 1118, method includes monitoring for detection of an input fromamong a tactile input and an audible speech input during the audibleoutputting of the received message. Method 1100 further includesdetermining at block 1120 if an input is detected. When no input isdetected, method iterates to block 1118 and continues to monitor for aninput. In response to detecting an input before completion of theaudible output, method 1100 includes pausing the audibly outputting ofthe received message (block 1122). Method 1100 then includes capturingaudible speech input and inserting the corresponding content (from thecaptured speech input) into the messaging interface (block 1124). Thisprocess can involve transcribing the audible speech input by forwardingthe captured speech input to a speech-to-text engine. In one embodimentthat supports transmission of the actual audible speech content, thecaptured speech is package in an audio file for transmission. Method1100 then includes, in response to detecting audible speech as the inputmethod, automatically forwarding content corresponding to the capturedaudible speech as a reply message to the received message (block 1126).Accordingly, the audible speech is audibly captured and the contentcorresponding to the audible speech is automatically forwarded as thereply message, without requiring any tactile manipulation of the device.

Referring now to FIG. 12, there is provided a method whereby specifictiming is provided to support use of audible input following dual inputactivation for an application, in accordance with one embodiment. Method1200 begins at start block and proceeds to block 1202 at which method1200 includes closing the tactile input device on detection of theaudible input before a tactile input and prior to expiration of thetimer. Method 1200 then includes monitoring for a pause in detectedaudible speech input (block 1204) and determining at block 1206 if thatpause is detected. In one embodiment, method 1200 includes forwardingthe detected audible speech to a speech-to-text engine for conversion tocorresponding text (block 1207), providing the corresponding text withina text box displayed in the CCP interface (block 1208), and appendingthe recently captured content to any previously captured content that ispresent within the CCP interface (block 1210). In response to detectinga pause in the speech input, method 1200 includes setting a first timerto track elapse time since a last detected audible speech (block 1212).Method 1200 also includes determining, at block 1214, if additionalspeech input is detected and whether (at block 1216) the timer hasexpired without receiving any additional speech input. According to oneembodiment, this time check involves comparing the elapsed time to apre-established end-of-speech input threshold time value. When the firsttimer expires without receiving additional input, the automatic captureof audible speech input is halted at the device, and the method 1200transitions to a message sending mode. Method 1200 further includes,setting a second timer to track elapsed time since the end of speechinput (block 1218), and then checking at block 1220 whether the secondtimer has expired without there being any addition input. In response tonot detecting any further input prior to expiration of the second timer,method 1200 includes automatically forwarding the content of thedetected speech presented within the CCP interface to the othermessaging participant. However, in response to detecting a tactile inputprior to expiration of the second timer, method 1200 includesautomatically opening the tactile input mechanism and the CCP interfacein an editing mode to present the captured content from the detectedaudible speech input (block 1224). The CCP interface is presented in theediting mode (i.e., a cursor provided within the interface to allowmanual editing therein) to allow the user to edit and/or append morecontent to the audibly captured message content. The use of a tactileinput mechanism to enter content or access the CCP interface terminatethe automatic forwarding option, and method 1200 then includesforwarding the reply message content only when the user selects the sendoption (block 1226). Method then terminates at end block.

In the above described flow chart, one or more of the methods may beembodied in a computer readable medium containing computer readable codesuch that a series of functional processes are performed when thecomputer readable code is executed on a computing device. In each of theflow charts of FIGS. 10, 11, and 12 presented herein, certain steps ofthe methods can be combined, performed simultaneously or in a differentorder, or perhaps omitted, without deviating from the spirit and scopeof the described innovation. While the method steps are described andillustrated in a particular sequence, use of a specific sequence ofsteps is not meant to imply any limitations on the innovation. Changesmay be made with regards to the sequence of steps without departing fromthe spirit or scope of the present innovation. Use of a particularsequence is therefore, not to be taken in a limiting sense, and thescope of the present innovation is defined only by the appended claims.

Aspects of the present innovation are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinnovation. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

As will be further appreciated, the processes in embodiments of thepresent disclosure may be implemented using any combination of software,firmware or hardware. Accordingly, aspects of the present disclosure maytake the form of an entirely hardware embodiment or an embodimentcombining software (including firmware, resident software, micro-code,etc.) and hardware aspects that may all generally be referred to hereinas a “circuit,” “module,” or “system.” Furthermore, aspects of thepresent disclosure may take the form of a computer program productembodied in one or more computer readable storage device(s) havingcomputer readable program code embodied thereon. Any combination of oneor more computer readable storage device(s) may be utilized. Thecomputer readable storage device may be, for example, but not limitedto, an electronic, magnetic, optical, electromagnetic, infrared, orsemiconductor system, apparatus, or device, or any suitable combinationof the foregoing. More specific examples (a non-exhaustive list) of thecomputer readable storage device would include the following: anelectrical connection having one or more wires, a portable computerdiskette, a hard disk, a random access memory (RAM), a read-only memory(ROM), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage device may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

According to one aspect, the program code that enables implementation ofthe disclosure can be provided as a computer program product, whichincludes a physical computer readable storage device having executableprogram code that when executed within a device having a microphone, adisplay and a communication component coupled to a processor executingsystem level firmware that supports receipt of audible and tactileinput. When executed by the processor, the program code enables thedevice to perform the functions of: detecting a tactile input thattriggers opening of a message reply interface; automatically openingboth a tactile input affordance and an audio input affordance(microphone) to enable selectable use of one of the two available typesof input affordances; visually indicating on a display of the devicethat the microphone is in active listening mode by displaying ananimated icon of the microphone; monitoring for a subsequent input fromamong additional tactile inputs and an audible speech input; and turningoff an input affordance that is not utilized to receive the subsequentinput.

The computer program product also includes program code that configuresthe device to perform the functions of: simultaneously opening anddisplaying an icon representing the microphone and a virtual tactileinput device (TID) when the tactile input mechanism is a virtual device;setting a timer to track an elapsed time after the simultaneous openingof the tactile input mechanism and the microphone; in response to theexpiration of the time without receiving any input, closing both thetactile input mechanism and the microphone; in response to tactilemanipulation of the virtual input device prior to expiration of thetime, removing the microphone icon from the display; and in response todetecting audible speech input prior to expiration of the timer,removing the virtual input device from the display.

While the innovation has been described with reference to exemplaryembodiments, it will be understood by those skilled in the art thatvarious changes may be made and equivalents may be substituted forelements thereof without departing from the scope of the innovation. Inaddition, many modifications may be made to adapt a particular system,device or component thereof to the teachings of the innovation withoutdeparting from the essential scope thereof. Therefore, it is intendedthat the innovation not be limited to the particular embodimentsdisclosed for carrying out this innovation, but that the innovation willinclude all embodiments falling within the scope of the appended claims.Moreover, the use of the terms first, second, etc. do not denote anyorder or importance, but rather the terms first, second, etc. are usedto distinguish one element from another.

The terminology used herein is for the purpose of describing particularembodiments only and is not intended to be limiting of the innovation.As used herein, the singular forms “a”, “an” and “the” are intended toinclude the plural forms as well, unless the context clearly indicatesotherwise. It will be further understood that the terms “comprises”and/or “comprising,” when used in this specification, specify thepresence of stated features, integers, steps, operations, elements,and/or components, but do not preclude the presence or addition of oneor more other features, integers, steps, operations, elements,components, and/or groups thereof.

The corresponding structures, materials, acts, and equivalents of allmeans or step plus function elements in the claims below are intended toinclude any structure, material, or act for performing the function incombination with other claimed elements as specifically claimed. Thedescription of the present innovation has been presented for purposes ofillustration and description, but is not intended to be exhaustive orlimited to the innovation in the form disclosed. Many modifications andvariations will be apparent to those of ordinary skill in the artwithout departing from the scope and spirit of the innovation. Theembodiment was chosen and described in order to best explain theprinciples of the innovation and the practical application, and toenable others of ordinary skill in the art to understand the innovationfor various embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method comprising: detecting activation, on adevice, of a content capturing and presenting (CCP) interface, whichreceives content that can be inputted via both speech-input andtactile-input; in response to the activation, a processor of the deviceautomatically enabling both (i) a tactile input mechanism for capturingtactile inputs and (ii) a microphone for capturing audible speechinputs; simultaneously opening and displaying, on a display of thedevice, both an icon representing the microphone and a virtual tactileinput device (TID) when the tactile input mechanism is a virtual device;setting a timer to track an elapsed time after the simultaneous openingof the tactile input mechanism and the microphone; monitoring fordetection of one of (i) a tactile input, which involves use of thetactile input mechanism to input the content and (ii) audible speech,which triggers use of the microphone to input the content; in responseto tactile manipulation of the virtual tactile input device prior toexpiration of the time, removing, by the processor, the microphone iconfrom the display and closing the microphone input; and in response todetecting audible speech, the processor: closing the tactile inputmechanism; enabling capturing of the audible speech via the microphone;and presenting content corresponding to the audible speech within theCCP interface on the display of the device.
 2. The method of claim 1,wherein automatically enabling the microphone further comprisesproviding at least one user-detectable indication that the microphone isin active listening mode, including at least one of (i) displaying ananimated icon of the microphone, (ii) outputting an audible tone via aspeaker of the device, (iii) performing a speech readout via thespeaker, and (iv) vibrating the device.
 3. The method of claim 1,further comprising: in response to the expiration of the time withoutreceiving any input, closing both the tactile input mechanism and themicrophone on the display; and in response to detecting audible speechinput prior to expiration of the timer, removing the virtual inputdevice from the display.
 4. The method of claim 1, wherein the CCPinterface is a messaging interface, and the method further comprises:detecting activation of a message element within a messaging applicationthat supports a messaging respondent replying to a received message viaboth speech-input and tactile-input; identifying whether a last messagewithin the message element is a received message, wherein a receivedmessage is a message that was created by another messaging participant,different from the messaging respondent, and received within themessaging element associated with the messaging respondent; and inresponse to detecting audible speech as the input method, automaticallyforwarding content corresponding to the captured audible speech as areply message to the received message, wherein the audible speech isaudibly captured and the content corresponding to the audible speech isautomatically forwarded as the reply message, without requiring tactilemanipulation of the device.
 5. The method of claim 4, furthercomprising: in response to the last message within the message elementbeing a received message: identifying whether the received message hasbeen previously accessed; and in response to the received message nothaving been previously accessed: if the received message is in textform, forwarding content of the received message to a text-to-speechengine to covert the text content to audible speech; audibly outputtingthe content of the received message; performing the automatic enablingof the tactile input mechanism and the microphone, wherein the receivedmessage is audibly outputted contemporaneously with the automaticallyenabling; monitoring for detection of an input from among a tactileinput and an audible speech input during the audible outputting of thereceived message; and pausing the audibly outputting of the receivedmessage in response to detecting the input.
 6. The method of claim 4,wherein identifying whether a last message within the message element isa received message comprises: identifying a hierarchy of messages withinthe message element, which hierarchy lists an order and time sequence ofentry of each message associated with the message element, including anymessages generated at a respondent side of the message exchange;identifying, as the received message, all messages in the hierarchy thatwere received subsequent to a most recent message generated by themessaging respondent within the message element; and in response tomultiple received messages not having been previously accessed,initiating audible outputting of the multiple received messages insequential order from a first received to a last received message;wherein the audible outputting of the content of the received messagecomprises reading out all messages identified as the received message intime order of receipt of the messages.
 7. The method of claim 1, furthercomprising: monitoring for a pause in detected audible speech input;tracking an elapsed time since a last detected audible speech andcomparing the elapsed time to an end-of-speech input threshold value; inresponse to detecting additional audible speech input before the elapsedtime exceeds the threshold value, adding content corresponding to thedetected additional audible speech input to previously captured content;and when the CCP interface is a messaging interface that capturescontent for transmission as a message: in response to the elapsed timeexceeding the threshold value: setting a second timer; visuallyindicating that the content of the received audible speech is about tobe transmitted to another messaging participant; and monitoring fordetection of one of an audio input and a tactile input prior toexpiration of the second timer; in response to not detecting any furtherinput prior to expiration of the second timer, automatically forwardingthe content of the detected speech presented within the message to theother messaging participant; in response to detecting a tactile input:automatically opening the tactile input mechanism and a text box of themessage having the content of the detected audible speech displayedtherein for editing and appending thereto; and forwarding a finalcontent of the message when a send message option is selected within themessaging interface.
 8. The method of claim 1, wherein: the tactileinput mechanism comprises at least one of a physical keyboard, a virtualkeyboard, and a virtual swipe box; the tactile input mechanism providestext content in response to user manipulation of an input affordancethat is associated with one of the device and the application; a devicesetting includes a default reply setting that supports a text basedreply to the received message and is configurable to a second replysetting that enables user selection of the microphone for speech basedreply when responding to the received message, based on detection ofuser initiation of audible speech following audible outputting of thereceived message; and the device setting includes a setting thatsupports reading out of received messages.
 9. A device comprising: aplurality of input devices including a speaker, a microphone capable ofcapturing audible speech inputs, and at least one tactile inputmechanism; a display device capable of displaying a plurality of userinterfaces and affordances; a memory comprising a firmware and at leastone application that generates a content capturing and presenting (CCP)interface, which receives content that can be inputted via bothspeech-input and tactile-input; a processor that is communicativelycoupled to the speaker, the microphone, the display device, the tactileinput mechanism, and the memory, and which executes program code of thefirmware and the application to activate the CCP interface; a userinterface controller communicatively connected with the plurality ofinput devices and the processor and that detects activation of the CCPinterface, wherein: the user interface controller, in response todetecting the activation of the CCP interface, triggers activation ofboth (i) a tactile input mechanism that captures tactile inputs and (ii)a microphone that captures audible speech inputs; the user interfacecontroller simultaneously opens and displays, on the display device,both an icon representing the microphone and a virtual tactile inputdevice (TID) when the tactile input mechanism is a virtual device; theprocessor sets a timer to track an elapsed time after the simultaneousopening of the tactile input mechanism and the microphone; the userinterface controller monitors for detection of one of (i) a tactileinput, detected at the tactile input mechanism, which involves use ofthe tactile input mechanism to input the content and (ii) audiblespeech, captured via the microphone, which triggers use of themicrophone to input the content; in response to tactile manipulation ofthe virtual input device prior to expiration of the time, the userinterface controller removes the microphone icon from the display andcloses the microphone input; and in response to detecting audiblespeech, the user interface controller: closes the tactile inputmechanism; and captures the audible speech via the microphone; and theprocessor presents content corresponding to the audible speech withinthe CCP interface on the display device.
 10. The device of claim 9,wherein, contemporaneously with automatically enabling the microphone,the processor provides user-detectable indication that the microphone isin active listening mode, by at least one of (i) displaying an animatedicon of the microphone, outputting an audible tone, (iii) performing aspeech readout, and (iv) vibrating the device.
 11. The device of claim9, wherein: in response to the expiration of the time without receivingany input, the user interface controller closes both the tactile inputmechanism and the microphone; and in response to detecting audiblespeech input prior to expiration of the timer, the user interfacecontroller removes the virtual input device from the display.
 12. Thedevice of claim 9, wherein: the CCP interface is a messaging interface;and the user interface controller: detects activation of a messageelement within a messaging application that supports a messagingrespondent replying to a received message via both speech-input andtactile-input; identifies whether a last message within the messageelement is a received message, wherein a received message is a messagethat was created by another messaging participant, different from themessaging respondent, and received within the messaging elementassociated with the messaging respondent; and in response to detectingaudible speech as the input method, automatically forwards contentcorresponding to the captured audible speech as a reply message to thereceived message, wherein the audible speech is audibly captured and thecontent corresponding to the audible speech is automatically forwardedas the reply message, without requiring tactile manipulation of thedevice.
 13. The device of claim 12, wherein: in response to the lastmessage within the message element being a received message, the userinterface controller: identifies whether the received message has beenpreviously accessed; and in response to the received message not havingbeen previously accessed: if the received message is in text form,forwards content of the received message to a text-to-speech engine tocovert the text content to audible speech; audibly outputs the contentof the received message; performs the automatic enabling of the tactileinput mechanism and the microphone, wherein the received message isaudibly outputted contemporaneously with the automatically enabling;monitors for detection of an input from among a tactile input and anaudible speech input during the audible outputting of the receivedmessage; and pauses the audibly outputting of the received message inresponse to detecting the input.
 14. The device of claim 12, wherein inidentifying whether a last message within the message element is areceived message, the processor: identifies a hierarchy of messageswithin the message element, which hierarchy lists an order and timesequence of entry of each message associated with the message element,including any messages generated at a respondent side of the messageexchange; identifies as the received message all messages in thehierarchy that were received subsequent to a most recent messagegenerated by the messaging respondent within the message element; and inresponse to multiple received messages not having been previouslyaccessed, initiates audible outputting of the multiple received messagesin sequential order from a first received to a last received message;wherein the audible outputting of the content of the received messagecomprises reading out all messages identified as the received message intime order of receipt of the messages.
 15. The device of claim 9,wherein: the user interface controller monitors for a pause in detectedaudible speech input; the processor tracks an elapsed time since a lastdetected audible speech and compares the elapsed time to anend-of-speech input threshold value; in response to detecting additionalaudible speech input before the elapsed time exceeds the thresholdvalue, the processor adds content corresponding to the detectedadditional audible speech input to previously captured content; and whenthe CCP interface is a messaging interface that captures content fortransmission as a message: in response to the elapsed time exceeding thethreshold value: the processor setting a second timer; the processorvisually indicates that the content of the received audible speech isabout to be transmitted to another messaging participant; and the userinterface controller monitors for detection of one of an audio input anda tactile input prior to expiration of the second timer; in response tonot detecting any further input prior to expiration of the second timer,the processor automatically forwards the content of the detected speechpresented within the message to the other messaging participant; inresponse to detecting a tactile input: the user interface controllerautomatically opens the tactile input mechanism and a text box of themessage having the content of the detected audible speech displayedtherein for editing and appending thereto; and the processor forwards afinal content of the message when a send message option is selectedwithin the messaging interface.
 16. The device of claim 9, wherein: thetactile input mechanism comprises at least one of a physical keyboard, avirtual keyboard, and a virtual swipe box; the tactile input mechanismprovides text content in response to user manipulation of an inputaffordance that is associated with one of the device and theapplication; a device setting includes a default reply setting thatsupports a text based reply to the received message and is configurableto a second reply setting that enables user selection of the microphonefor speech based reply when responding to the received message, based ondetection of user initiation of audible speech following audibleoutputting of the received message; and the device setting includes asetting that supports reading out of received messages.
 17. A computerprogram product comprising: a physical computer readable storage devicehaving executable program code that when executed within a device havinga microphone, a display and a communication component coupled to aprocessor executing system level firmware that supports receipt ofaudible and tactile input, the program code enables the device toperform the functions of: detecting a tactile input that triggersopening of a message reply interface; automatically opening both atactile input affordance and an audio input affordance (microphone) toenable selectable use of one of two available types of inputaffordances; simultaneously opening and displaying an icon representingthe microphone and a virtual tactile input device (TID) when the tactileinput mechanism is a virtual device; visually indicating on a display ofthe device that the microphone is in active listening mode by displayingan animated icon of the microphone; setting a timer to track an elapsedtime after the simultaneous opening of the tactile input mechanism andthe microphone; monitoring for a subsequent input from among additionaltactile inputs and an audible speech input; in response to tactilemanipulation of the virtual input device prior to expiration of thetime, removing the microphone icon from the display; and turning off aninput affordance that is not utilized to receive the subsequent input.18. The computer program product of claim 17, further comprising programcode that configures the device to perform the functions of: in responseto the expiration of the time without receiving any input, closing boththe tactile input mechanism and the microphone; in response to detectingaudible speech input prior to expiration of the timer, removing thevirtual input device from the display.